Release 10.1A: OpenEdge Deployment:
WebClient Applications

Using WebClient’s authentication dialogs in your application

Suppose your application needs to access the AppServer and the following are true:

The same AppServer contains application components to be downloaded and business logic to be accessed by your application.
The security cache does not contain authentication information, and the application detects this.
Note: This set of conditions occurs when WebClient has not yet downloaded any as-needed application components from the AppServer.

To access the AppServer in this situation, your application can prompt the end user for security items by displaying the security dialogs that WebClient uses. This provides the end user with a consistent interface.

These routines reside, in the form of procedure (.r) files, in the WebClient installation at OpenEdge-Install-Directory\wcadd. Also, if some but not all the required values are available from the CODEBASE-LOCATOR handle, they can be passed in as default values, allowing the user to fill in the remaining values.

When using the dialog boxes, consider the following:

To make the dialogs look exactly the same as when WebClient invokes them, obtain the prompt input parameter from CODEBASE-LOCATOR:END-USER-PROMPT.
Before calling an authentication dialog, the application is responsible for obtaining the relevant attribute values from the CODEBASE-LOCATOR handle to pass to these routines. For example, the value of NOT PERSISTENT-CACHE-DISABLED should be passed for the second parameter, enable-persistent-checkbox.
After calling an authentication dialog, the application is responsible for setting the appropriate CODEBASE-LOCATOR attributes with the information obtained from the end user.